System for providing alerts to members of defined local geographical groups

ABSTRACT

A system and method are disclosed for creating groups associated with defined geographical neighborhoods for the purpose of providing and distributing information to members of the neighborhood groups, and soliciting assistance from members of the neighborhood groups. For example, an alert concerning a missing child may be sent from a user device (e.g., smart phone) to a server located on the Internet for distribution to user devices of members of a neighborhood groups. The notified members, in turn, using their respective user devices, may send notifications to the alert-originating user (as well as other members) of their participation in the search for the missing child. Additionally, the notified members may send notifications to the alert-originating user of the finding of the lost child. Such features may also apply to other alerts and/or notifications sent to members of a neighborhood group.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and is a divisional of U.S.Non-provisional application Ser. No. 13/051,999, entitled “SYSTEM ANDMETHOD FOR PROVIDING ALERTS TO MEMBERS OF DEFINED LOCAL GEOGRAPHICALGROUPS”, filed on Mar. 18, 2011, and which is herein incorporated byreference.

FIELD

This invention relates generally to communication systems, and inparticular, to a system and method for providing alerts to members of adefined local geographical group.

BACKGROUND

Many children are lost every day. Often, the parent or legal guardianquickly finds the child by simply searching the area or vicinity inwhich the child was last known to be. However, in other circumstances,the parent or legal guardian is not able to find the lost child withinan hour or more. In such circumstances, the parent or legal guardian maycontact local law enforcement authority to assist in the finding of thechild. The involvement of local authority may also lead to thesuccessful finding of the lost child.

In more dire circumstances, for example, when a child has been lost forseveral hours or days, the parent or legal guardian will often attemptto get the local community involved in the searching for the lost child.In this regard, the parent or legal guardian may create flyers with apicture of the lost child and pertinent information, and place theflyers at various locations around the local neighborhood. Additionally,the parent or legal guardian may telephone neighbors, friends andacquaintances in the neighborhood to ask them for assistance insearching for the child.

Such traditional methods for locating lost children have many drawbacks.For instance, the chances or probability of a lost child being foundgenerally decreases non-linearly over time. Thus, it is desirable forthe lost child to be found quickly as soon as his/her disappearance isknown. However, the traditional ways of locating a lost child, such ascontacting the local authority or seeking the assistance of members ofthe local community, often take substantial amount of time. In the caseof contacting local authority, often the local authority has legalrestraints before it can commence a search for a lost child or person.And, in the case of contacting members of the local community, this isusually a time-consuming tasks.

SUMMARY

An aspect of the disclosure relates to a system, method, and devices forestablishing one or more neighborhood groups for transmitting variouslocal information to members of the one or more neighborhood groups,respectively. Such local information may relate to an alert concerning alost or missing child proximate or within a defined geographicalneighborhood associated with a neighborhood group. Alternatively, or inaddition to, such local information may relate to an alert concerning afound child located proximate or within a defined geographicalneighborhood associated with a neighborhood group. Alternatively, or inaddition to, such local information may relate to lost persons(regardless of age), found persons (regardless of age), lost pets,crimes, and elderly and disabled people care proximate or within adefined geographical neighborhood associated with a neighborhood group.

To effectuate such related functionality, the system includes a servercoupled to a wide area network (WAN), such as the Internet. The serveris adapted to create neighborhood group data objects upon requests ofusers. Each neighborhood group data object includes information relatedto the associated neighborhood, such as the name or identity of theneighborhood; information related to the users or members of theneighborhood group, such as in the form of a plurality of user profiledata objects; and information related to pending notifications, such asin the form of notification data objects, including lost child dataobject, found child data object, lost pet data object, local crime dataobject, elderly/disabled care request data object, and others.

A user, using a user device, communicates with the server, via the WANand/or a cellular telephone network, to, for example, create aneighborhood group, administer or manage the neighborhood group, sendinvitation to candidate users to join the neighborhood group, andreceive and approve (or deny) requests from users to join a neighborhoodgroup. Additionally, a user, using a user device, may sendnotifications, such as lost child alerts, found child alerts, lost petalerts, crime alerts, and care requests, to members of a neighborhoodgroup to seek assistance with (or to merely inform them of) the alerts.Further, a user, using a user device, may receive such notifications asa member of a neighborhood group, volunteer to assist in the nature ofthe notifications, and report back to the originators informationconcerning the notifications, such as the finding of the missing childor pet, or the identity of the parent or legal guardian of the foundchild, or evidence related to a crime, or an indication that the userwill assist in a particular care requests.

The system is valuable because potentially current and accuratelocal-related information may be quickly provided to people residingproximate or within a defined geographical neighborhood. These people,or members of the corresponding neighborhood group, are more apt to beinterested in the information, to participate in helping with a solutionto a local alert, and to take preventive measures to lesson thelikelihood of mishappenings from occurring proximate or within thedefined geographical neighborhood.

Other aspects, advantages and novel features of the present disclosurewill become apparent from the following detailed description whenconsidered in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary communication systemin accordance with an aspect of the disclosure.

FIG. 2A illustrates a flow diagram of an exemplary method of creating anew user for local alert services in accordance with another aspect ofthe disclosure.

FIG. 2B illustrates a diagram of an exemplary screen associated withcreating a new user for local alert services in accordance with anotheraspect of the disclosure.

FIG. 2C illustrates a diagram of an exemplary screen associated withlogging in an existing user for local alert services in accordance withanother aspect of the disclosure.

FIG. 3A illustrates a flow diagram of an exemplary method of creating anew neighborhood group for local alert services in accordance withanother aspect of the disclosure.

FIG. 3B-3C illustrate diagrams of exemplary screens associated withcreating a new neighborhood group for local alert services in accordancewith other aspects of the disclosure.

FIG. 3D illustrates a flow diagram of an exemplary method of joining anexisting neighborhood group for local alert services by a user inaccordance with another aspect of the disclosure.

FIG. 3E-3I illustrate diagrams of exemplary screens associated withjoining an existing neighborhood group for local alert services inaccordance with other aspects of the disclosure.

FIG. 4A illustrates a flow diagram of an exemplary method of adding achild to a user profile for local alert services in accordance withanother aspect of the disclosure.

FIG. 4B-4E illustrate diagrams of exemplary screens associated withadding a child to a user profile for local alert services in accordancewith other aspects of the disclosure.

FIG. 5A illustrates a flow diagram of an exemplary method of creating alost child alert for a neighborhood group in accordance with anotheraspect of the disclosure.

FIG. 5B-5H illustrate diagrams of exemplary screens associated withcreating a lost child alert for a neighborhood group in accordance withother aspects of the disclosure.

FIG. 6A illustrates a flow diagram of an exemplary method of joining asearch effort for a lost child alert associated with a neighborhoodgroup in accordance with another aspect of the disclosure.

FIG. 6B-6C illustrate diagrams of exemplary screens associated withjoining a search effort for a lost child alert associated with aneighborhood group in accordance with other aspects of the disclosure.

FIG. 7A illustrates a flow diagram of an exemplary method of notifying auser originating a lost child alert of the finding of the childassociated with a neighborhood group in accordance with another aspectof the disclosure.

FIG. 7B-7D illustrate diagrams of exemplary screens associated withnotifying a user originating a lost child alert of the finding of thechild associated with a neighborhood group in accordance with otheraspects of the disclosure.

FIG. 8A illustrates a flow diagram of an exemplary method of creating afound child alert for a neighborhood group in accordance with anotheraspect of the disclosure.

FIG. 8B illustrates a diagram of an exemplary screen associated withcreating a found child alert for a neighborhood group in accordance withanother aspect of the disclosure.

FIG. 8C illustrates a flow diagram of an exemplary method of respondingto a found child alert for a neighborhood group by a user in accordancewith another aspect of the disclosure.

FIGS. 8D-8E illustrate a diagram of an exemplary screen associated withresponding to a found child alert for a neighborhood group by a user inaccordance with other aspects of the disclosure.

FIG. 9 illustrates a flow diagram of an exemplary method of creating acrime alert for a neighborhood group in accordance with another aspectof the disclosure.

FIG. 10 illustrates a flow diagram of an exemplary method of creating acare request for a neighborhood group in accordance with another aspectof the disclosure.

FIG. 11 illustrates a block diagram of an exemplary local alert serverin accordance with another aspect of the disclosure.

FIG. 12 illustrates a block diagram of an exemplary user device inaccordance with another aspect of the disclosure.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

FIG. 1 illustrates a block diagram of an exemplary communication system100 in accordance with an aspect of the disclosure. In summary, thecommunication system facilitates providing alerts and/or otherinformation to members of a user-defined neighborhood group. In thisregards, a user may create a new or join an existing neighborhood group.Each member of the neighborhood group may send alerts and/or otherinformation to the remaining members of the neighborhood groups.Additionally, any participating law enforcement, fire station, civicleaders and/or other government agencies local to the neighborhood mayreceive and/or provide such alerts and information as needed. Asexamples, such local alerts may include missing or lost child, lostperson (regardless of age, e.g., a person with Alzheimers), found child,found person (regardless of age, e.g., a person with Alzheimers) lostpet, crime, fire, gas leak, flooding, mudslide, etc. Other informationmay include upcoming local community events, requests forelderly/disabled care, local fund raising activities, etc.

Using the communication system 100, members of the neighborhood group,including local government agencies, may participate in the alerts. Asan example, with regard to a lost child alert, members of theneighborhood group may volunteer to search for the lost child. Duringsuch alert, the local law enforcement agency may be notified of the lostchild, and may decide to send an agent to investigate and help with thesearch. Additionally, in case the lost child is found by a member, thecommunication system 100 facilitates providing notification of the foundchild to the user that originated the lost child alert, as well as othermembers of the neighborhood group and participating government agency oragencies. Although as detailed below, a lost or found child alert mayserve to exemplify features and advantages of a neighborhood group, itshall be understood that other alerts and information may be transmittedto members of a neighborhood group.

More specifically, as discussed in more detail below, the communicationsystem 100 facilitates the following: (1) signing up a new user forlocal alert services; (2) logging in an existing user for local alertservices; (3) creating or defining a new neighborhood group by a user;(4) joining an existing neighborhood group by a user; (5) adding one ormore children to a user profile data object for alerts and/or otherpurposes; (6) creating a lost child alert by a user; (7) joining asearch for a lost child by one or more user members of a neighborhoodgroup; (8) notifying a user who originated the lost child alert of thefinding of the lost child by a user member of a neighborhood group; (9)creating a found child alert by a user; (10) responding to a found childalert by a user member of a neighborhood group; (11) creating a crimealert by a user member of a neighborhood group; and (12) creating a carerequest by a user member of a neighborhood group.

With regard to implementation, the communication system 100 may comprisea wide area network (WAN) 102, such as the Internet, a local alertserver 110 coupled to the WAN 102, a user device 112 (e.g., desktop orlaps computer) coupled to the WAN 102, a cellular network 104 coupled tothe WAN 102 and including a plurality of base stations (BS) 106, and auser wireless device 114 (e.g., a smart phone) communicatively coupledto one of the base stations (BS) 106. Via the WAN 102 and/or thecellular network 104, the local alert server 110 provides neighborhoodalert and/or information distribution services to users using, forexample, the user device 112 and the user wireless device 114. The localalert server 110 may provide such services via a website and webpagestransmitted to users of devices 112 and 114, or by interacting withapplications running on those devices, or any combination thereof. Thedetailed discussion of examples of the services provided by the localalert server 110 now follows.

FIG. 2A illustrates a flow diagram of an exemplary method 200 ofcreating a new user for local alert services in accordance with anotheraspect of the disclosure. According to the method 200, a candidate user,desiring services provided by the local alert server 110, accesses a“new user” screen using, for example, the user device 112 or device 114(block 202). The “new user” screen may be provided to the user device112 or 114 via a webpage or HTML document, or may be provided by asoftware application running on the device 112 or 114. This applies toall of the screens mentioned herein. Using the “new user” screen, thecandidate user enters particular information requested by the localalert server 110 (block 204). For example, the information requested maybe the user's email address, telephone number, proposed password, and/orother information.

Then, according to the method 200, the candidate user, using the userdevice 112 or 114, transmits a new user requests with the information tothe local alert server 110 (block 206). In the case of user device 112,the request and information are sent to the local alert server 110 byway of the WAN 102. In the case of user wireless device 114, the requestand information are sent to the local alert server 110 via the cellularnetwork 104 and the WAN 102. The transmission of information from userdevices 112 and 114, as further described herein, may be communicated tothe local alert server 110 via these paths.

In response to receiving the request and the user information, the localalert server 110, after determining that the request and the userinformation are acceptable, creates a user profile data object andstores it in a local or remote database (e.g., a computer-readablemedium) (block 208). As an example, the request and user information maybe accepted if the proposed password meets defined guidelines forpasswords, the user email address and mobile phone number arelegitimate, and the user accepted a legal agreement associated with theservices provided by the local alert server 110. After creating the userprofile data object, the local alert server 110 sends a “new user”confirmation with an active log-in status to the device 112 or 114 ofthe new user (block 210). The confirmation is sent to the user device112 via the WAN 102 or to the wireless device 114 via the WAN 102 andthe cellular network 104. The transmission of information from the localalert server 110 to the user devices 112 and 114, as further describedherein, may be communicated via the these paths.

FIG. 2B illustrates a diagram of an exemplary user device screen 250associated with creating a new user for local alert services inaccordance with another aspect of the disclosure. The screen 250comprises a title section identifying the application, for example, the“LOCAL ALERT APPLICATION.” Under the title section, the screen 250includes a sub-title indicating the purpose of the screen, for example,new user “SIGN UP.” Additionally, the screen 250 provides several datainput objects for receiving information requested for new users, such asuser's “Email Address”, “Mobile Phone”, “Create Password” and “Agree tothe terms” associated with the services. Finally, the screen 250includes a data transmission object for initiating the transmission ofthe information to the local alert server 110, such as the “SIGN UP”soft button. It shall be understood that “new user” screen 250 is merelyan example, and may be configured differently to achieve the same orsimilar objectives.

FIG. 2C illustrates a diagram of an exemplary user device screen 260associated with logging in an existing user for local alert services inaccordance with another aspect of the disclosure. If a user is notcurrently logged in the local alert server 110 for receiving servicestherefrom, the screen 260 may be accessed by an existing user to log inthe server. Similar to the previous screen 250, the screen 260 comprisesa title identifying the application, for example, the “LOCAL ALERTAPPLICATION,” a sub-title indicating the purpose of the screen, forexample, user “LOG IN,” and several data input objects for receiving login information, such as user's “Email Address” and “Password.”Additionally, the screen 260 includes a data transmission object forinitiating the transmission of the log in information to the local alertserver 110, such as the “LOG IN” soft button. Finally, if a candidateuser accesses this screen by mistake, the screen 260 provides a link tothe “SIGN UP” screen 250, previously discussed. It shall be understoodthat “LOG IN” screen 260 is merely an example, and may be configureddifferently to achieve the same or similar objectives.

FIG. 3A illustrates a flow diagram of an exemplary method 300 ofcreating a new neighborhood group for local alert services in accordancewith another aspect of the disclosure. Once a user has registered withthe local alert server 110, the user may create a new neighborhood groupfor the purpose of providing alerts and information to future members ofthe group. The neighborhood, as described herein, is a geographical areadefined by a user that is local to where the user resides, such as acity, a neighborhood within a city, a common zip code area, or otherrelatively small area not defined by governmental boundaries. It iswithin this defined neighborhood where members of the group would beinterested in alerts and information local to the correspondingneighborhood.

More specifically, according to the method 300, an existing orauthorized user of the local alert server 110 accesses a “neighborhoodsetup” screen using the user device 112 or 114 (block 302). Using the“neighborhood setup” screen, the user defines the geographical boundaryand other parameters of the proposed neighborhood group (block 304). Theparameters for the new neighborhood group may include the name for theneighborhood group, the administrator of the neighborhood group, adescription of the neighborhood group, and/or others. Once the user hasentered the requested information, the user, using the “neighborhoodsetup” screen, transmits a neighborhood group setup request with theentered information to the local alert server 110 (block 306). Inresponse to receiving and accepting the request, the local alert server110 creates a neighborhood group data object with the geographicalboundary and parameter information, and stores it in an accessibledatabase (block 308). The local alert server 110 may also modify theuser profile data object of the requesting user to denote that the useris a member of the newly-created neighborhood group (block 310). Thelocal alert server 110 may then send a confirmation of the setup of thenew neighborhood to the user device 112 or 114 of the requesting user(block 312).

FIG. 3B illustrates a diagram of an exemplary user device screen 320 fordefining a geographical boundary associated with a new neighborhoodgroup in accordance with another aspect of the disclosure. Similar toprevious screens, the screen 320 comprises a title identifying theapplication, for example, the “LOCAL ALERT APPLICATION,” and a sub-titleindicating the purpose of the screen, for example, “DEFINE NEIGHBORHOODBOUNDARY.” Additionally, the screen 320 comprises a graphical inputobject 322 depicting a map of the geographical area-of-interest. A user,for example, may manipulate typical map navigation features, such aszoom-in, zoom-out, pan, or otherwise enter the user's zip code to honein on the geographical area-of-interest for the new neighborhood group.

The graphical input object 322 includes a drawing object 324, such assquares, which may be added, dragged and removed to allow a user todefine the geographical boundary 326 for the new neighborhood group. Forinstance, in this example, the geographical boundary is indicated by theshaded area superimposed on the map. As shown, the defined geographicalarea is bounded by main street (between 1^(st) and 3^(rd) avenues) and Astreet (between 3^(rd) and 4^(th) avenues) from the North; by 3^(rd)avenue (between Main and A streets, and D and E streets) and 4^(th)avenue (between A and D streets) from the East; by D street (between3^(rd) and 4^(th) avenues) and E street (between Pt and 3^(rd) avenues)from the South; and by 1^(st) avenue (between Main and E streets) fromthe West. Finally, the screen 320 comprises a data transmission objectfor initiating the transmission of the geographical boundary informationto the local alert server 110, such as the “SUBMIT” soft button. Itshall be understood that the screen 320 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 3C illustrate a diagram of an exemplary user device screen 330 fordefining other parameters of the new neighborhood group in accordancewith another aspect of the disclosure. Similar to the previous screens,the screen 330 comprises a title identifying the application, forexample, the “LOCAL ALERT APPLICATION,” and a sub-title indicating thepurpose of the screen, for example, “DEFINE NEIGHBORHOOD PARAMETERS.”Additionally, the screen 330 includes data input objects for receivingneighborhood group parameter information, such as “Neighborhood Name”,“Neighborhood Administrator”, and “Neighborhood Description.” Finally,the screen 330 comprises a data transmission object for initiating thetransmission of the neighborhood group parameter information to thelocal alert server 110, such as the “SUBMIT” soft button. It shall beunderstood that the screen 330 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 3D illustrates a flow diagram of an exemplary method 340 of joiningan existing neighborhood group for local alert services by a user inaccordance with another aspect of the disclosure. In this scenario,other users have previously created neighborhood groups thatare-of-interest to the current user. That is, these previously-createdneighborhood groups are probably in the vicinity of where the currentuser resides. Accordingly, instead of creating a new neighborhood group,the current user may opt to search for neighborhood groups that are ofinterests, and select one or more of such groups to requests membershiptherein.

In this regard, according to the method 340, the user accesses a “selectneighborhood group” screen using the user device 112 or 114 (block 342).Based on the user's profile information (e.g., resident zip code), the“select neighborhood” screen may pre-populate a list of candidateneighborhood groups that would be of interest to the user. Using thescreen, the user selects a neighborhood group among the list to join asa member (block 344). Based on the selection, the user device 112 or 114may determine whether the user has previously received an invite fromthe administrator of the selected neighborhood group (block 346). If theuser has already received the invite, then the user device 112 or 114transmits a joining confirmation to the local alert server 110 (block350). In response to receiving the joining confirmation, the local alertserver 110 modifies the corresponding neighborhood group data object toindicate the user as a member, and modifies the user profile data objectto indicate that the user is now a member of the selected neighborhoodgroup (block 354). The local alert server also sends a confirmation tothe user that he/she is now a member of the requested neighborhood group(block 358).

If, on the other hand, the user device 112 or 114 determines that theadministrator has not sent an invite to the user in block 346, the userdevice transmits a requests to the indicated neighborhood administratorby way of the local alert server 110 (block 348). Then, the local alertserver 110 determines if it has received the approval from theneighborhood administrator (block 352). If it has, then the local alertserver 110 modifies the corresponding neighborhood group data object toindicate the user as a member, and modifies the user profile data objectto indicate that the user is now a member of the selected neighborhoodgroup (block 354), and notifies the user per block 358. If, on the otherhand, the local alert server 110 determines that the membership requestwas denied by the neighborhood administrator, the local alert serversends a rejection notice to the user device 112 or 114 (block 356). Thelocal alert server 110 may indicate that the membership request has beendenied by either receiving an affirmative denial from the neighborhoodadministrator, or not receiving a response to the request from theneighborhood administrator within a defined time period after therequest was issued (e.g., the request has timed-out).

FIG. 3E illustrates a diagram of an exemplary user device screen 360associated with a user joining an existing neighborhood group inaccordance with another aspect of the disclosure. This screen 360 may bepresented to the user in order to filter out neighborhood groups thatwould probably not be of interest to the user, and present the user alist of neighborhoods that may be of interest to the user based on wherehe/she resides. More specifically, the screen 360 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example,“SELECT NEIGHBORHOOD.” Additionally, the screen 360 includes a datainput object adapted to receive a zip code (e.g., 92603) associated withthe resident of the user. Using the zip code, the user device 112 or 114may filter out neighborhood groups that are geographically located adefined distance beyond the relevant zip code, and present a list ofneighborhood groups that are geographically located within the defineddistance from the relevant zip code. It shall be understood that thescreen 360 is merely an example, and may be configured differently toachieve the same or similar objectives.

FIG. 3F illustrates a diagram of an exemplary user device screen 365associated with a user joining an existing neighborhood group inaccordance with another aspect of the disclosure. After the user hasentered his/her zip code, the user device 112 or 114 may present a listof neighborhood groups that may be of interest to the user based on theentered zip code. More specifically, the screen 365 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example,“SELECT NEIGHBORHOOD.” Additionally, the screen 365 includes a datainput object in the form of a list of selectable neighborhood groups.For instance, in this example, the identified groups includeIrvine-Turtle Rock, Irvine-Shady Canyon, Irvine-Quail Hill,Irvine-Woodbridge, and Newport Coast. In response to a selection made bythe user, the user device 112 or 114 transmits a correspondingmembership request to the local alert server 110 for approval or denialby the neighborhood administrator. It shall be understood that thescreen 365 is merely an example, and may be configured differently toachieve the same or similar objectives.

FIG. 3G illustrates a diagram of an exemplary user screen 370 associatedwith a user joining an existing neighborhood group in accordance withanother aspect of the disclosure. In the previous examples, the userinitiated the process of selecting a neighborhood group. However, itshall be understood that the process may be initiated by theneighborhood administrator sending an invite to the user. Screen 370 isrelevant to this scenario. More specifically, the screen 370 comprises atitle identifying the application, for example, the “LOCAL ALERTAPPLICATION,” and a sub-title indicating the purpose of the screen, forexample, “SELECT NEIGHBORHOOD.” Additionally, the screen 370 includes astatement indicating that the user has been invited to be a member of aparticular neighborhood group (e.g., Irvine-Turtle Rock), and a datainput object to allow the user to accept or deny the invitation. Itshall be understood that the screen 370 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 3H illustrates a diagram of an exemplary user device screen 375associated with a user joining an existing neighborhood group inaccordance with another aspect of the disclosure. Once a user has sent arequest for membership in a particular neighborhood group or hasaccepted an invitation to the neighborhood group, the local alert server110 may send a confirmation of membership in the group to the user.Screen 375 is relevant to this scenario. More specifically, the screen375 comprises a title identifying the application, for example, the“LOCAL ALERT APPLICATION,” and a sub-title indicating the purpose of thescreen, for example, “SELECT NEIGHBORHOOD.” Additionally, the screen 375includes a statement indicating that the user has been accepted to therequested or invited neighborhood group (e.g., Irvine-Turtle Rock). Itshall be understood that the screen 375 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 3I illustrates a diagram of an exemplary user device screen 380associated with a user joining an existing neighborhood group inaccordance with another aspect of the disclosure. Once a user has sent arequest for membership in a particular neighborhood group, the localalert server 110 may inform the user that membership to the requestedneighborhood group has been denied. Screen 380 is relevant to thisscenario. More specifically, the screen 380 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example,“SELECT NEIGHBORHOOD.” Additionally, the screen 380 includes a statementindicating that the user has been denied membership to the requestedneighborhood group (e.g., Irvine-Turtle Rock). It shall be understoodthat the screen 380 is merely an example, and may be configureddifferently to achieve the same or similar objectives.

FIG. 4A illustrates a flow diagram of an exemplary method 400 of addinga child to a user profile data object for local alert services inaccordance with another aspect of the disclosure. One advantage, amongmany, for being a member of a neighborhood group is that one may send analert concerning one's child to the group in order to get assistancefrom group members concerning the nature of the alert. As furtherexemplified in more detail herein, one such alert may concern a lostchild. Accordingly, members of the neighborhood group, in being notifiedof a lost child alert, may volunteer in searching for the child, as wellas reporting back to the group if and when the child is found. To assista user in sending alerts regarding his/her child or children, the userprofile data object may be modified to include information and anelectronic picture or video of his/her child or children. The method 400is relevant to this scenario.

According to the method 400, a user accesses a “child setup” screen onthe user device 112 or 114 (block 402). Using the screen, the userenters information related to a child (block 404). For example, suchinformation may include child's name, gender, date of birth, and/orother information. Additionally, using a data input object on thescreen, the user inputs an electronic picture (or video) of the child(block 408). This may be accomplished by the user taking a picture ofthe child using a camera built into the user device 112 or 114, orretrieving a preexisting picture of the child from a memory residing inthe user device 112 or 114. Further, using the screen, the user may thentransmit the child information and picture (or video) to the local alertserver 110 (block 410). The local alert server 110 then modifies theuser profile data object to include the child information and electronicpicture (or video) (block 412). The local alert server 110 may then senda confirmation to the user indicating that the child was successfullyadded to the user's profile (block 414). The method 400 may be repeated,as needed, to add additional child or children to the user's profile.

FIG. 4B illustrates a diagram of an exemplary user device screen 420associated with adding a child to a user profile data object inaccordance with another aspect of the disclosure. The screen 420 may bethe first screen a user accesses to begin the processes of adding achild to his/her profile. More specifically, the screen 420 comprises atitle identifying the application, for example, the “LOCAL ALERTAPPLICATION,” and a sub-title indicating the purpose of the screen, forexample, “CHILD SETUP.” Additionally, the screen 420 includes data inputobjects adapted to receive the name, gender and data-of-birth of thechild. Additionally, the screen 420 includes a data input object toreceive an electronic picture (or video) of the child. Finally, thescreen 420 includes a data transmission object (e.g., the “SAVE” softbutton) adapted to transmit the child information and picture to thelocal alert server 110. It shall be understood that the screen 420 ismerely an example, and may be configured differently to achieve the sameor similar objectives.

FIG. 4C illustrates a diagram of an exemplary user device screen 430associated with adding a child to a user profile data object inaccordance with another aspect of the disclosure. The screen 430 may bepresented in response to a user activating the picture input object ofscreen 420. More specifically, the screen 430 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example,“CHILD SETUP (Add Picture).” Additionally, the screen 430 includes adata input object adapted to receive a selection from the user as to thesource of the child's picture. In this example, the screen 430 allows auser to select the gallery or memory as the source of the child'spicture, or to select the camera as the source of the child's picture.It shall be understood that the screen 430 is merely an example, and maybe configured differently to achieve the same or similar objectives.

FIG. 4D illustrates a diagram of an exemplary user device screen 440associated with adding a child to a user profile data object inaccordance with another aspect of the disclosure. The screen 440 allowsa user to remove a child picture from his/her profile. This may beuseful if the current pictures in the profile are old, and do notaccurately represent the current appearance of the child. This screen440 may be presented to the user after a particular picture of the childhas been selected for removal. More specifically, the screen 440comprises a title identifying the application, for example, the “LOCALALERT APPLICATION,” and a sub-title indicating the purpose of thescreen, for example, “CHILD SETUP (Remove Picture).” Additionally, thescreen 440 includes a data input object adapted to receive aconfirmation or not from the user as to the removal of the selectedchild picture. It shall be understood that the screen 440 is merely anexample, and may be configured differently to achieve the same orsimilar objectives.

FIG. 4E illustrates a diagram of an exemplary user device screen 450associated with adding a child to a user profile data object inaccordance with other aspects of the disclosure. The screen 450facilitates a user to transmit a child information and picture to thelocal alert server 110 for the purpose of adding the child to the user'sprofile. More specifically, the screen 450 comprises a title identifyingthe application, for example, the “LOCAL ALERT APPLICATION,” and asub-title indicating the purpose of the screen, for example, “CHILDSETUP (Saved).” Additionally, the screen 450 includes a data inputobject adapted to receive an indication from the user as to whether toadd additional one or more children to the user's profile. If the userindicates in the affirmative, the process of adding the childinformation and picture is repeated for the next child. It shall beunderstood that the screen 450 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 5A illustrates a flow diagram of an exemplary method 500 ofcreating a lost child alert for a neighborhood group in accordance withanother aspect of the disclosure. The method 500 is applicable when amember of a neighborhood group has a missing child, and needs theassistance of other members of the group, as well as local lawenforcement, in locating the child. In receiving the lost child alert,the other members and the participating law enforcement agency, shouldhave current information and picture of the child to better assist themin locating the child.

More specifically, a user, with the missing child, accesses a “lostchild alert” screen provided by the user device 112 or 114 (block 502).Using the screen, the user selects the child of which the alert is to besent (block 504). Further, using the screen, the user transmits thealert to the local alert server 110 (block 506). In response toreceiving the alert, the local alert server 110 creates a lost childalert data object to keep track of information relevant to the alert(block 508). Then, the local alert server 110 transmits the alerts tomembers of the one or more neighborhood groups of which the user ismember, as well as any law enforcement agency associated with the one ormore neighborhood groups (block 510).

FIG. 5B illustrates a diagram of an exemplary user device screen 520associated with creating a lost child alert in accordance with anotheraspect of the disclosure. In particular, the screen 520 facilitates auser in selecting a child of which the lost child alert is to betransmitted. More specifically, the screen 520 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example, “LOSTCHILD ALERT.” Additionally, the screen 520 includes a data input objectto receive a selection of a child of which the lost child alert is to becreated. In this example, the screen 520 indicates that the user hasfour (4) children in his/her profile (namely, Johnny Doe, Jaime Doe,Lisa Doe, and Eric Doe). Also, in this example, the alert button isactivated for Lisa Doe, and not the other children. Thus, Lisa Doe isthe child pertaining to the lost child alert. It shall be understoodthat the screen 520 is merely an example, and may be configureddifferently to achieve the same or similar objectives.

FIG. 5C illustrates a diagram of an exemplary user device screen 525associated with creating a lost child alert in accordance with anotheraspect of the disclosure. In particular, the screen 525 facilitates auser in editing the lost child's information and picture before thealert is sent. For example, this screen 525 may be presented to the userin response to the user clicking the child's name in screen 520. Morespecifically, the screen 525 comprises a title identifying theapplication, for example, the “LOCAL ALERT APPLICATION,” and a sub-titleindicating the purpose of the screen, for example, “LOST CHILD ALERTEDIT.” Additionally, the screen 525 includes data input objects adaptedto receive edits to the name, gender, and date-of-birth of the child.Additionally, the screen 525 includes a data input object to receive apicture (or video) of the child. Accordingly, this screen 525 helps auser to ensure that the information and picture of the child is currentwhen the alert is sent. Finally, the screen 525 includes a datatransmission object (e.g., the “SAVE” soft button) adapted to transmitthe edits to the child information and picture (or video) to the localalert server 110. It shall be understood that the screen 525 is merelyan example, and may be configured differently to achieve the same orsimilar objectives.

FIG. 5D illustrates a diagram of an exemplary user device screen 530associated with creating a lost child alert in accordance with anotheraspect of the disclosure. In particular, the screen 530 facilitates auser to confirm the sending of the lost child alert. This screen 530 maybe presented to the user in response to the user initiating the alertvia the screen 520. More specifically, the screen 530 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example, “LOSTCHILD ALERT.” Also, the screen 530 may indicate that this is the firstof two screens for completing the lost child alert process.Additionally, the screen 530 includes the information (e.g., Lisa Doe, 8years old) and a picture of the child. Further, the screen 530 includesan edit link adapted to display the edit child screen 525, previouslydiscussed. Finally, the screen 530 includes a soft button (e.g., >Go toStep 2) to allow the user to navigate to the next screen concerning theconfirmation of the lost child alert. It shall be understood that thescreen 530 is merely an example, and may be configured differently toachieve the same or similar objectives.

FIG. 5E illustrates a diagram of an exemplary user device screen 535associated with creating a lost child alert in accordance with anotheraspect of the disclosure. In particular, the screen 535 is an example ofthe second screen that facilitates a user confirming the transmission ofthe lost child alert. This screen 535 may be presented to the user inresponse to the user activating the “Go to Step 2” soft button of screen530. More specifically, the screen 535 comprises a title identifying theapplication, for example, the “LOCAL ALERT APPLICATION,” and a sub-titleindicating the purpose of the screen, for example, “LOST CHILD ALERT.”Also, the screen 535 may indicate that this is the second of two screensfor completing the lost child alert process. Additionally, the screen535 may also include a first data input object (e.g., a scroll-downmenu) to receive the child's last known location via a selection by theuser, a second data input object (e.g., a text box) to receive adescription from the user concerning the child's last known location,and a third data input object (e.g., another text box) to receive otherrelevant information (e.g., the clothes the child was wearing) from theuser. Finally, the screen 530 includes a data transmission object (e.g.,Activate Missing Child Alert) to allow the user to transmit the childalert with the relevant information to the local alert server 110. Itshall be understood that the screen 530 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 5F illustrates a diagram of an exemplary user device screen 540associated with creating a lost child alert in accordance with anotheraspect of the disclosure. The screen 540 may be presented to the userafter he/she has transmitted the lost child alert to the local alertserver 110, and allows the user an opportunity to cancel the alert. Thismay be useful in the case the user finds the child shortly aftertransmitting the lost child alert. More specifically, the screen 540comprises a title identifying the application, for example, the “LOCALALERT APPLICATION,” and a sub-title indicating the purpose of thescreen, for example, “LOST CHILD ALERT.” Also, the screen 540 providesan indication that the alert is being transmitted, and an object (e.g.,Cancel) for initiating a cancellation of a previously-transmitted alert.It shall be understood that the screen 540 is merely an example, and maybe configured differently to achieve the same or similar objectives.

FIG. 5G illustrates a diagram of an exemplary user device screen 545associated with creating a lost child alert in accordance with anotheraspect of the disclosure. The screen 545 may be presented to the userafter he/she has activated the cancel button of screen 540 to allow theuser to confirm whether the alert is to be cancelled. More specifically,the screen 545 comprises a title identifying the application, forexample, the “LOCAL ALERT APPLICATION,” and a sub-title sub-sectionindicating the purpose of the screen, for example, “LOST CHILD ALERT.”Also, the screen 545 provides a data transmission object (e.g., Yes) toconfirm the transmission of the alert cancellation to the local alertserver 110, and an input object (e.g., No) to halt the alertcancellation. It shall be understood that the screen 545 is merely anexample, and may be configured differently to achieve the same orsimilar objectives.

FIG. 5H illustrates a diagram of an exemplary user device screen 550associated with a lost child alert in accordance with another aspect ofthe disclosure. The screen 550 may be presented to the user after thelocal alert server 110 has issued the lost child alert. The screen 550provides the user originating the alert with a current status of thelost child alert. More specifically, the screen 550 comprises a titleidentifying the application, for example, the “LOCAL ALERT APPLICATION,”and a sub-title indicating the purpose of the screen, for example, “LOSTCHILD ALERT.” The screen 550 further provides information as to thestatus of the lost child, for example, the time that has elapsed sincethe alert was issued (e.g., Searching for 14 minutes), the number ofusers searching for the child (e.g., 27 Active Users are searching), andthe radius of users to which the alert was sent (e.g., Notified allcontacts within a 5 mile radius). Thus, the alert may be sent to allmembers of the neighborhood group or those members that reside within adefined radius of the user.

Additionally, the screen 550 may provide a data transmission object(e.g., Refresh Status) for transmitting a request for currentinformation concerning the alert to the local alert server 110. Inresponse to the request, the local alert server 110 accesses thecorresponding lost child alert data object for current informationconcerning the alert, and transmits the current information to the userdevice 112 or 114. Furthermore, the screen 550 provides “real-time”information (e.g., pop-ups) indicating updates to the search status(e.g., Bart joined search and Child found by Bart (view)). If one ofthese “real-time” pop-ups indicate that the child has been found, it mayalso serve as a data transmission object for transmitting a request forinformation concerning the found child. Finally, the screen 550 includesanother data transmission object (e.g., Cancel Search) to transmit acancel alert request to the local alert server 110. This allows the userto cancel the alert in case the child is found. It shall be understoodthat the screen 550 is merely an example, and may be configureddifferently to achieve the same or similar.

FIG. 6A illustrates a flow diagram of an exemplary method 600 of joininga search for a lost child alert associated with a neighborhood group inaccordance with another aspect of the disclosure. As previouslydiscussed, one advantage of a neighborhood group is that alerts may besent to the members to have at least some of them assist in resolvingthe alert. In this regard, the method 600 describes how a member, thathas received a lost child alert, may participate in the search for themissing child.

According to the method 600, a user receives a notification of a lostchild alert on the user device 112 or 114 from the local alert server110 (block 602). In response to the received alert, the user device 112or 114 generates a screen concerning the lost child alert (block 604).For example, such screen may provide information about the lost child(e.g., name, gender, age, etc.), as well as an electronic picture of thechild. Additionally, the screen may provide a data transmission objectto allow the user to transmit a notice to the local alert server 110that he/she will participate in the search for the missing child.Accordingly, using the screen, the user indicates that he/she will jointhe search (block 606). In response, the user device 112 or 114transmits the notice that the user has joined the search for the childto the local alert server 110 (block 608). In response to receiving thenotification, the local alert server 110 updates the lost child dataobject to indicate that the user has joined the search (block 610). Suchinformation in the lost child data object may be accessed by the memberthat issued the alert, as well as other members and participating locallaw enforcement agency.

FIG. 6B illustrate a diagram of an exemplary user device screen 620associated with a lost child alert in accordance with other aspects ofthe disclosure. The screen 620 may be an exemplary “desktop” screendepicting the available applications on the user device 112 or 114. Asindicated, the screen 620 includes a graphical icon representing thelocal alert application. In addition, a graphical object (e.g., thenumber “1” encircled) superimposed on the application icon may be usedto summons the user of pending alerts. For instance, in this example,the graphical object indicates that there is one (1) pending alert. Theuser may then open the local alert application in order to ascertain thedetails concerning the alert. It shall be understood that the screen 620is merely an example, and may be configured differently to achieve thesame or similar objectives.

FIG. 6C illustrates a diagram of an exemplary user device screen 630associated with a lost child alert in accordance with another aspect ofthe disclosure. In particular, the screen 630 provides information to auser, that did not originate the alert, concerning an active lost childalert. More specifically, the screen 630 comprises a title identifyingthe application, for example, the “LOCAL ALERT APPLICATION,” and asub-title indicating the purpose of the screen, for example, “LOST CHILDALERT.” Also, the screen 630 may indicate an additional sub-title“Active Missing Child Alert.” Further, the screen 630 includesinformation concerning the lost child (e.g., Lisa Doe, 8 years old) andan electronic picture of the child. Finally, the screen 630 includes adata transmission object (e.g., Join Search Efforts) for transmitting anotification to the local alert server 110 that the user is going tojoin the search for the missing child. It shall be understood that thescreen 630 is merely an example, and may be configured differently toachieve the same or similar objectives.

FIG. 7A illustrates a flow diagram of an exemplary method 700 ofnotifying a user originating a lost child alert of the finding of thechild in accordance with another aspect of the disclosure. Obviously, afavorable outcome of the lost child alert is the finding of the missingchild. As previously discussed, the local alert server 110 assists inachieving such a favorable outcome by communicating the lost child alertto members of neighborhood group. Also, as previously discussed, membersof the neighborhood group are able to join the search efforts for themissing child. Accordingly, method 700 is applicable when a member hasfound the missing child.

More specifically, according to the method 700, a user accesses a “lostchild status screen” using the user device 112 or 114 (block 702). Usingthe screen, the user activates a found child soft button (block 704). Inresponse, the user device 112 or 114 generates a screen indicating thecontact information of the user originating the alert, and including aninput object to receive an electronic photograph of the child (block706). At such time, the user may contact the user originating the alert.Alternatively, or in addition to, the user may input an electronicpicture of the child using the input object (block 708). In response tothe user activating a send button on the screen, the child picture andcurrent location (e.g., by accessing a GPS module located on the userdevice 112 or 114) are sent to the local alert server 110 (block 710).The local alert server 110 updates the lost child data object with thereceived information and picture (block 712), and sends the informationand picture to the user originating the alert (block 714). Thealert-originating user may send a notification to the local alert server110 confirming the identity of the child (block 716). The local alertserver 110 then updates the lost child data object to indicate thefinding of the child (block 718).

FIG. 7B illustrates a diagram of an exemplary user device screen 730associated with a lost child alert in accordance with another aspect ofthe disclosure. The screen 730 may be presented to a member of aneighborhood group that has received a lost child alert, and may havejoined the search for the missing child. More specifically, the screen730 comprises a title identifying the application, for example, the“LOCAL ALERT APPLICATION,” and a sub-title indicating the purpose of thescreen, for example, “LOST CHILD ALERT.” The screen 730 further providesinformation as to the status of the lost child, for example, the timethat has elapsed since the alert was issued (e.g., Searching for 14minutes) and the number of users searching for the child (e.g., 27Active Users are searching). Additionally, the screen 730 provides adata transmission object (Update Current Status) adapted to send arequest to the local alert server 110 for the current informationrelated to the alert.

Further, the screen 730 provides instruction in the case the userhappens to find the child (“If you spot Lisa Doe, please click the“Found Child). Finally, the screen 730 includes a first datatransmission object (Found Child) adapted to initiate the process ofnotifying the local alert server 110 that the user has found the missingchild, and a second data transmission object (Remove Me) to send arequest to the local alert server 110 to remove the user from the searchefforts for the child. It shall be understood that the screen 730 ismerely an example, and may be configured differently to achieve the sameor similar objectives.

FIG. 7C illustrates a diagram of an exemplary user device screen 740associated with a lost child alert in accordance with another aspect ofthe disclosure. The screen 740 may be presented to a member of aneighborhood group that has activated the Found Child button on screen730. More specifically, the screen 740 comprises a title identifying theapplication, for example, the “LOCAL ALERT APPLICATION,” a firstsub-title indicating the purpose of the screen, for example, “LOST CHILDALERT,” and a second sub-title “Found Child.” The screen 740 furtherprovides a data input object adapted to receive an electronic picture ofthe child. Additionally, the screen 740 includes a statement that thecurrent location of the user as well as the child's picture will be sentto the local alert server 110. Finally, the screen 740 includes a datatransmission object (Send) adapted to send the child's picture andlocation information to the local alert server 110. It shall beunderstood that the screen 740 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 7D illustrates a diagram of an exemplary screen 750 associated witha lost child alert in accordance with another aspect of the disclosure.The screen 750 may be presented to a member of a neighborhood group thathas activated the Send button on screen 740. More specifically, thescreen 750 comprises a title identifying the application, for example,the “LOCAL ALERT APPLICATION,” a first sub-title indicating the purposeof the screen, for example, “LOST CHILD ALERT,” and a second sub-title“Report Sent.” The screen 750 further provides a statement indicatingthat the reporting of the found child was sent to the user issuing themissing child alert. Additionally, the screen 750 includes a statementindicating that the alert remains active until the alert originatorterminates it. It shall be understood that the screen 750 is merely anexample, and may be configured differently to achieve the same orsimilar objectives.

FIG. 8A illustrates a flow diagram of an exemplary method 800 ofcreating a found child alert for a neighborhood group in accordance withanother aspect of the disclosure. In the previous (“lost child”)scenario, the alert concerned a missing child pertaining to the useroriginating the alert, such as a parent, legal guardian or caretaker. Inthe “found child” scenario, a user finds a lost child not associatedwith the user. In this case, the user wants to send a found child alertin order to reunite the child with his/her parent, legal guardian orcaretaker.

In this regard, the user accesses a “found child alert” screen providedby the user device 112 or 114 (block 802). Using the screen, the userenters information regarding the found child (block 802). For example,such information may include the child's name, gender, age and locationat which the child was found. Additionally, using the screen, the usermay input an electronic picture of the child (block 806). Finally, usingthe screen, the user transmits the information and child picture to thelocal alert server 110 (block 808). The local alert server 110, in turn,creates a found child data object (block 810), and transmits the foundchild alert to members of the user's neighborhood group, and/or thatreside within a defined radius of the location at which the child wasfound, and/or a participating local law enforcement agency (block 812).

FIG. 8B illustrates a diagram of an exemplary user device screen 820associated with creating a found child alert in accordance with anotheraspect of the disclosure. In particular, the screen 820 facilitates auser sending a found child alert with information relevant to the childas well as an electronic picture of the child. More specifically, thescreen 820 comprises a title identifying the application, for example,the “LOCAL ALERT APPLICATION,” and a sub-title indicating a purpose ofthe screen, for example, “FOUND CHILD ALERT.” Additionally, the screen820 includes data input objects adapted to receive the found child'sname, gender, age, and location at which the child was found. The screen820 also includes a data input object to receive an electronic picture(or video) of the child. Finally, the screen 820 includes a datatransmission object (e.g., “SEND ALERT” soft button) adapted to transmitthe child information and picture to the local alert server 110. Itshall be understood that the screen 820 is merely an example, and may beconfigured differently to achieve the same or similar objectives.

FIG. 8C illustrates a flow diagram of an exemplary method 830 ofresponding to a found child alert by a user (e.g., parent, legalguardian, caretaker, friend) who knows the child in accordance withanother aspect of the disclosure. According to the method 830, the userreceives a found child alert on his/her user device 112 or 114 sent bythe local alert server 110 (block 832). In response to the alert, theuser accesses a found child alert status screen (block 834). Using thescreen, the user indicates whether he/she is the legal guardian or knowsthe identity of the legal guardian (block 836). Additionally, using thescreen, the user transmits the indicated information regarding the legalguardian to the local alert server (block 838). The local alert server110 updates the found child data object with the information (block840). The local alert server 110 then transmits the finder's contactinformation to the user (block 842).

FIG. 8D illustrates a diagram of an exemplary user device screen 850associated with a found child alert in accordance with another aspect ofthe disclosure. In particular, the screen 850 facilitates a userresponding to a found child alert by indicating that he/she is the legalguardian or knows the legal guardian. More specifically, the screen 850comprises a title identifying the application, for example, the “LOCALALERT APPLICATION,” and a sub-title indicating a purpose of the screen,for example, “FOUND CHILD ALERT.” Additionally, the screen 850 includesa statement indicating the identity of the person that found the child,the child's age, and the location at which the child was found. Also,the screen 850 includes an electronic picture of the child. The screen850 provides a data input object adapted to receive information as towhether the user is the legal guardian of the child or knows the legalguardian. Finally, the screen 850 includes a data transmission object(e.g., “Send” soft button) adapted to transmit the user's legal guardianstatus information to the local alert server 110. It shall be understoodthat the screen 850 is merely an example, and may be configureddifferently to achieve the same or similar objectives.

FIG. 8E illustrates a diagram of an exemplary user device screen 860associated with a found child alert in accordance with another aspect ofthe disclosure. In particular, the screen 860 provides contactinformation of the child's finder to a user associated with the child.More specifically, the screen 860 comprises a title identifying theapplication, for example, the “LOCAL ALERT APPLICATION,” and a sub-titleindicating a purpose of the screen, for example, “FOUND CHILD ALERT.”Additionally, the screen 860 provides the identity and contactinformation of the child's finder (“You may contact Mary Wilson at (xxx)xxx-xxx.”). It shall be understood that the screen 860 is merely anexample, and may be configured differently to achieve the same orsimilar objectives.

FIG. 9 illustrates a flow diagram of an exemplary method 900 of creatinga crime alert for a neighborhood group in accordance with another aspectof the disclosure. In the previous examples, the alerts involved a lostchild. However, it shall be understood that the local alert applicationdescribed herein need not be limited to missing people applications. Forexample, other relevant information, such as a lost pet, lost person(regardless of age), found person (regardless of age), etc. may beprovided to members of one's neighborhood group. In the exampleregarding method 900, the alert concerns a crime observed or reportednear the vicinity of the neighborhood.

More specifically, according to the method 900, a user accesses a crimealert screen on his/her user device 112 or 114 (block 902). Using thescreen, the user enters information related to the observed or reportedcrime (block 904). For example, the information may include the natureof the crime, the location, the time it happened, victim information,and other relevant information. Further, using the screen, the usertransmits the crime alert including the entered information to the localalert server 110 (block 906). The local alert server 110, in turn,creates a crime alert data object to include the received informationregarding the crime (block 908). Finally, the local alert server 110transmits an alert concerning the crime to members of the user'sneighborhood group and any associated law enforcement agency (block910). This information may be useful to law enforcement agency insolving the crime, as well as to members of the neighborhood group intaking crime prevention and reporting measures.

FIG. 10 illustrates a flow diagram of an exemplary method 1000 ofcreating a care volunteer request for a neighborhood group in accordancewith another aspect of the disclosure. The neighborhood group describedherein may also be useful in providing assistance to elderly anddisabled residents of the neighborhood. In this regard, members of theneighborhood group may send care calendar alerts requesting volunteersfor assisting people, including the particular assistance needed, andthe corresponding the dates and times.

More specifically, according to the method 1000, a user accesses a “carecalendar” screen on his/her user device 112 or 114 (block 1002). Usingthe screen, the user views information, for example in a calendarformat, related to requests for specified care for identified people(block 1004). As discussed above, such information may include theidentity of the people needing assistance, the nature of the assistance,and the relevant locations, dates, times and duration of the requestedcare. Using the screen, the user selects one or more of the carerequests to volunteer for (block 1006). Also, using the screen, the usertransmits the volunteer request to the local alert server 110 (block1008). The local alert server 110, in turn, updates a corresponding carerequest data object to include the received information regarding thevolunteer (block 1010). In this way, people needing care may getassistance from people in their neighborhood.

FIG. 11 illustrates a block diagram of an exemplary local alert server1100 in accordance with another aspect of the disclosure. The server1100 may be an exemplary implementation of the local alert server 110previously discussed. In particular, the local alert server 110comprises a processor 1102, a network interface 1104, and acomputer-readable medium 1106. The processor 1102 performs the definedoperations for the server 1100 as previously discussed with respect toneighborhood groups and alerts. The network interface 1104 is adapted totransmit and receive information to and from a wide area network (WAN),such as the Internet. As previously discussed, such information istransmitted to and received from user devices, law enforcement systems,and other devices as described herein. And, the computer-readable medium1106 is adapted to store one or more software modules configured tocontrol the processor 1102 in performing its defined operations. Thecomputer-readable medium 1106 (e.g., a non-transitory medium) may alsostore data, such as user profile data objects, neighborhood group dataobjects, alert data objects, and other data as described herein, for useby the processor 1102 in performing its defined operations.

FIG. 12 illustrates a block diagram of an exemplary user device 1200 inaccordance with another aspect of the disclosure. The user device 1200may be an exemplary implementation of user device 112 and/or 114,previously discussed. In particular, the user device 1200 comprises aprocessor 1202, a network or wireless interface 1204, acomputer-readable medium 1206, user interface modules 1208, a GPS module1214, and a camera module 1210. The processor 1202 performs the definedoperations for the user device 1200 as previously discussed with respectto neighborhood groups and alerts. The network or wireless interface1204 is adapted to transmit and receive information to and from a widearea network (WAN), such as the Internet, and/or, a cellular network. Aspreviously discussed, such information is transmitted to and receivedfrom a local alert server as described herein. The computer-readablemedium 1206 (e.g., a non-transitory medium) is adapted to store one ormore software modules configured to control the processor 1202 inperforming its defined operations. The computer-readable medium 1206 mayalso store data as described herein for use by the processor 1202 inperforming its defined operations.

The user interface modules 1208, which may comprise a keyboard,microphone, display, speaker, etc., allows a user to provide informationto and receive information from the processor 1202 in accordance withthe processes described herein. The GPS module 1214 provides informationto the processor 1202 as to the current geographical location of theuser device 1200 for the particular applications described herein. Thecamera module 1210 is adapted to provide still pictures or video to theprocessor 1202 for the purposes described herein.

While the invention has been described in connection with variousembodiments, it will be understood that the invention is capable offurther modifications. This application is intended to cover anyvariations, uses or adaptation of the invention following, in general,the principles of the invention, and including such departures from thepresent disclosure as come within the known and customary practicewithin the art to which the invention pertains.

What is claimed is:
 1. A user device, comprising: a network interfaceadapted to interface with a wide area network (WAN) or cellular network;a user input device; and a processor adapted to: receive a firstinstruction from a user to send a first notification to users of aneighborhood group by way of the user input device, wherein theneighborhood group is associated with a defined geographicalneighborhood; and transmit the first notification to a server by way ofthe network interface for distribution of information based on the firstnotification to users of the neighborhood group by the server.
 2. Theuser device of claim 1, wherein the first notification relates to analert of a lost child.
 3. The user device of claim 2, wherein the firstnotification includes following: information related to an identity orphysical characteristic of the lost child; information related to a lastknown location of the lost child; and an electronic picture or video ofthe lost child.
 4. The user device of claim 3, further comprising adisplay, wherein the processor is adapted to generate a screen on thedisplay with one or more data input objects to receive said information.5. The user device of claim 2, wherein the processor is further adaptedto: receive a second instruction from the user to send a secondnotification to users of the neighborhood group by way of the user inputdevice, wherein the second notification indicates a finding of the lostchild; and transmit the second notification to the server by way of thenetwork interface for distribution of information based on the secondnotification to users of the neighborhood group by the server.
 6. Theuser device of claim 2, wherein the processor is adapted to receive asecond notification from the server via the network interface, whereinthe second notification indicates a finding of the lost child.
 7. Theuser device of claim 1, wherein the first notification relates to analert concerning a found child.
 8. The user device of claim 6, whereinthe first notification includes the following: information related to anidentity or physical characteristic of the found child; informationrelated to a known location where child was found; and an electronicpicture or video of the found child.
 9. The user device of claim 1,wherein the first notification relates to a crime allegedly or in-factcommitted within or proximate the geographical neighborhood.
 10. Theuser device of claim 1, wherein the first notification relates to arequest for volunteer care for a person living within or proximate thegeographical neighborhood.
 11. The user device of claim 1, wherein thefirst notification relates to an alert concerning a lost pet.
 12. A userdevice, comprising: a network interface adapted to interface with a widearea network (WAN) or cellular network; a user interface device; and aprocessor adapted to: receive a first notification originating from auser of a neighborhood group from a server via the network interface,wherein the neighborhood group is associated with a defined geographicalneighborhood; and provide information based on the first notification toa user via the user interface device.
 13. The user device of claim 12,wherein the first notification relates to an alert concerning a lostchild.
 14. The user device of claim 13, wherein the first notificationincludes the following: information related to an identity or physicalcharacteristic of the lost child; information related to a last knownlocation of the lost child; and an electronic picture or video of thelost child.
 15. The user device of claim 13, wherein the processor isfurther adapted to: receive a second instruction by way of the userinterface device to send a second notification to users of the definedneighborhood group, wherein the second notification indicates that theuser has joined a search effort for the lost child; and transmit thesecond notification to the server by way of the network interface fordistribution of information based on the second notification to users ofthe neighborhood group by the server.
 16. The user device of claim 13,wherein the processor is further adapted to: receive a secondinstruction by way of the user interface device, to send a secondnotification to users of the defined neighborhood group, wherein thesecond notification indicates that the user found the lost child; andtransmit the second notification to the server by way of the networkinterface for distribution of information based on the secondnotification to users of the neighborhood group by the server.
 17. Theuser device of claim 12, wherein the first notification relates to analert concerning a found child.
 18. The user device of claim 17, whereinthe first notification includes the following: information related to anidentity or physical characteristic of the found child; informationrelated to a known location where child was found; and an electronicpicture or video of the found child.
 19. The user device of claim 17,wherein the processor is further adapted to: receive a secondinstruction by way of the user interface device, to send a secondnotification to users of the defined neighborhood group, wherein thesecond notification indicates that the user is or knows someoneassociated with the found child; and transmit the second notification tothe server by way of the network interface for distribution ofinformation based on the second notification to users of theneighborhood group by the server.
 20. The user device of claim 12,wherein the first notification relates to a crime allegedly or in-factcommitted within or proximate the geographical neighborhood.
 21. Theuser device of claim 12, wherein the first notification relates to arequest for volunteer care for a person living within or proximate thegeographical neighborhood.
 22. The user device of claim 12, wherein thefirst notification relates to an alert concerning a lost pet.
 23. A userdevice, comprising: a network interface adapted to interface with a widearea network (WAN) or cellular network; a user interface device; and aprocessor adapted to: receive a first instruction to send a request tocreate a neighborhood group from a user via the user interface device,wherein the neighborhood group is associated with a defined geographicalneighborhood; and transmit the request to a server via the networkinterface.
 24. The user device of claim 23, wherein the request includesthe following: information related to an identity of the neighborhoodgroup; information related to a geographical boundary of theneighborhood; and information related to an identity of an administratorof the neighborhood group.
 25. The user device of claim 24, wherein theinformation related to the geographical boundary of the neighborhoodcomprises a plurality of coordinates identifying points along thegeographical boundary.
 26. The user device of claim 23, wherein theprocessor is further adapted to: receive a request from the server viathe network interface for another user to join the neighborhood group;and transmit a response to the request to the server via the networkinterface, wherein the response is received from the user via the userinterface device.
 27. The user device of claim 23, wherein the processoris further adapted to: receive a second instruction to send an invite toanother user to join the neighborhood group from the user via the userinterface; and transmit the invite to the server via the networkinterface for subsequent transmission to the another user by the server.